Cancel Allocation fails to reset the state of the source shard when moving #4457
Assignees
Labels
Comments
ghost
assigned
s1monw
added a commit
that referenced
this issue
Dec 16, 2013
Currently we miss to reset the source shards status to ACTIVE if we cancel a relocation. If the shard is RELOCATING we need to reset to state ACTIVE. Closes #4457
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
Currently we miss to reset the source shards status to ACTIVE if we cancel a relocation. If the shard is RELOCATING we need to reset to state ACTIVE. Closes elastic#4457
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Currently we miss to reset the source shards status to ACTIVE if we cancel a relocation. If the shard is RELOCATING we need to reset to state ACTIVE. Closes elastic#4457
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we move a shard from Node
Ato NodeBand cancel the relocation the source node still remains in stateRELOCATING.The text was updated successfully, but these errors were encountered: